home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
007a
/
pafabl12.zip
/
PAFABLTY.CHG
< prev
next >
Wrap
Text File
|
1991-10-04
|
4KB
|
72 lines
PAFAbility Change History
V1.2 released 7 Oct 1991
XMS support was added to handle the NAME2.DAT file and to hold the index
page being formatted for printing.
The following situations were corrected:
Spelling of "Twelvth" was changed to "Twelfth".
On the cascading report, the progenitor of the second and subsequent
lines had the same person number as the last person in the previous
line.
Unpredictable results occurred when "seenotes" was used in a date field.
V1.1 released 1 Aug 1991
Bug fix only, no enhancements. The following situations were corrected:
Occasionally, some event data may not have been printed and/or event
data for one person may have been repeated for a later person.
In some cases, the child's numbers were not printed. This occurred when
the child had no individual event data, had marriage data, notes were to
be printed and the child had no notes.
The INDEX.TMP file is now deleted when it is no longer needed.
In some cases, the individual's name or the marriage data was repeated
after the event data for that person. This only occurred when notes were
to be printed and the individual's record indicated that there were
notes, but there really weren't any. This condition occurs when the
individual had notes that were deleted via the PAF note editor rather
than through the "delete all notes" option of the FR notes menu. In the
second situation, FR deletes the notes and sets the note pointer to
zero. In the first situation, the notes are deleted but the note pointer
is left pointing to the first note block.
Some index pages were printed on two pages instead of one, or a long
name may have had garbage printed as the last character of the page
numbers. This only happened when an index column entry was the maximum
size allowed.
If a single line report was requested, and the selected individual had
multiple marriages with no children from the first marriage, the program
went into an infinite loop.
Some people get a message indicating not enough memory for the index
array when there appears to be sufficient memory. I've changed things
around so this shouldn't happen anymore.
Tip: Use the name frequency option to see how many names in your name file
are not being used. If there are a lot, you might consider using GIE to
create a GEDCOM file of your entire database, then importing the GEDCOM
file to a new FR database. This will eliminate the unused names which
means the smaller name file will use less memory. Another benefit to
doing this is that the NOTES2.DAT file will be defragmented - each
person's notes will be all together, rather than strung out through the
file as they were entered. This makes retrieval of the notes a little
faster. However, keep in mind that any deleted records in the INDIV2.DAT
and MARR2.DAT files will be eliminated and the remaining records will
have different RINs and MRINs.
Tip: If you store your notes in text files and want them to show up on your
reports, you can clone your database with GEDCOM to make a temporary
database with the notes in the internal file. The GIE program dated June
1990 or later will include text file notes in the GEDCOM file.
V1.0 21 June 1991 First release